Re: [GENERAL] Deadlock on Linux - Mailing list pgsql-general

From Herouth Maoz
Subject Re: [GENERAL] Deadlock on Linux
Date
Msg-id l03110703b289736f0b03@[147.233.159.109]
Whole thread Raw
In response to Deadlock on Linux  (Anand Surelia <anand@bytekinc.com>)
List pgsql-general
At 21:50 +0200 on 30/11/98, Anand Surelia wrote:


> I am running Postgres 6.3.2 on Caldera Linux 2.0.35. There are a few
> scripts written in Perl using Pg.pm which tune up the database nightly.
> They've been running for more than three months. However, since last
> month one of the scripts is failing to execute, giving the following
> message
> NOTICE:  Deadlock detected -- See the lock(l) manual page for a possible
> cause.
>
> There is no entry for lock in section 1 of the man on my system. There
> is one entry however for lock which says that this call is not
> implemented in the Linux kernel 1.2.4 and it returns a -1 always.

No, no, no! It's not in section 1 (one), it's section l (lowercase L)...
That is, the PostgreSQL SQL manual pages... (Someone should have thought
about that confusion...)

LOCK is an SQL command in Postgres, and its manpage explains all about
deadlocks.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma



pgsql-general by date:

Previous
From: Gregory Maxwell
Date:
Subject: Can't upgrade to 6.4
Next
From: Alessandro Baldoni
Date:
Subject: PostgreSQL 6.3.2, 6.4 on Irix